Outbound Market Data Server Recovery (OMD – CHX to SIP Quotes and Trades, Clearing, Bookfeed and TRF)

Services Involved	Impacts	Response
Services MAY include any of the following: Bookfeed, SIP Regional Inputs, Clearing/DTCC and DTRF and all related database loaders. ServiceTypes MAY include any of the following: BFS, QRS, TRS, CLR, DTCC, DTRF and DLBF, DLAR, DLTR, DLRT	During Trading Hours: - Trading suspension should only be considered if recovery takes longer than 5 minutes. -Outbound quotes will be queued in 29west Data Store to be sent to database upon QRS restart. All Matching Engine top of book orders will be re-quoted when QRS process reconnects after restart. -Outbound trades will be queued in 29west Data Store to be sent to SIP “sold” upon TRS restart. -Outbound clearing will be queued and resent upon RTC and DTCC restarts/reconnects. -Outbound messages from Brokerplex to TRF will queue to be sent upon DTRF restart/reconnect. -Bookfeed quote and trade messaging will be queued in 29west Data Store to be sent in chronological order upon BFS restart (as if all Bookfeed Subscribers requested a retransmission of this data). During Off-Trading Hours: - Trading suspension should only be considered if recovery goes past 6am.	- Notify EXECUTIVE - Notify SIPs, DTCC and/or DTRFs affected. - Move applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and NAT addresses are pre-defined. - No configuration changes necessary. -All UTDRI (NASDAQ TRS) database loading must be up to date in the data center that the ME is going to be restarted in before restarts occur. The only time a database loader file should move between nodes is if the database loading has not been completed and can only be completed by doing so. - DTCC and DTRF Fix Engine files need to be moved ahead of service restart. - BFS log and index files need to be moved ahead of service restart to accommodate later Bookfeed Retransmission Requests. - Restart order (as applicable by server): QRS, TRS, DTCC, CLR, DTRF, BFS then database loaders. - Confirm all data accounted for around move. - Database loader files (not moved by necessity) can be concatenated after end of day shutdown. SEE APPLICATION SPECIFIC RECOVERY DOCUMENTATION FOR MORE INFORMATION, IF NEEDED.

Services Involved

Impacts

Response

Services MAY include any of the following:

Bookfeed, SIP Regional Inputs, Clearing/DTCC and DTRF and all related database loaders.

ServiceTypes MAY include any of the following:

BFS, QRS, TRS, CLR, DTCC, DTRF and

DLBF, DLAR, DLTR, DLRT

During Trading Hours:

- Trading suspension should only be considered if recovery takes longer than 5 minutes.

-Outbound quotes will be queued in 29west Data Store to be sent to database upon QRS restart. All Matching Engine top of book orders will be re-quoted when QRS process reconnects after restart.

-Outbound trades will be queued in 29west Data Store to be sent to SIP “sold” upon TRS restart.

-Outbound clearing will be queued and resent upon RTC and DTCC restarts/reconnects.

-Outbound messages from Brokerplex to TRF will queue to be sent upon DTRF restart/reconnect.

-Bookfeed quote and trade messaging will be queued in 29west Data Store to be sent in chronological order upon BFS restart (as if all Bookfeed Subscribers requested a retransmission of this data).

During Off-Trading Hours:

- Trading suspension should only be considered if recovery goes past 6am.

- Notify EXECUTIVE

- Notify SIPs, DTCC and/or DTRFs affected.

- Move applications to alternate nodes.

- If alternate nodes not available, move to DR nodes.

- All hosts and NAT addresses are pre-defined.

- No configuration changes necessary.

-All UTDRI (NASDAQ TRS) database loading must be up to date in the data center that the ME is going to be restarted in before restarts occur. The only time a database loader file should move between nodes is if the database loading has not been completed and can only be completed by doing so.

- DTCC and DTRF Fix Engine files need to be moved ahead of service restart.

- BFS log and index files need to be moved ahead of service restart to accommodate later Bookfeed Retransmission Requests.

- Restart order (as applicable by server):

QRS, TRS, DTCC, CLR, DTRF, BFS then database loaders.

- Confirm all data accounted for around move.

- Database loader files (not moved by necessity) can be concatenated after end of day shutdown.

SEE APPLICATION SPECIFIC RECOVERY DOCUMENTATION FOR MORE INFORMATION, IF NEEDED.